Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eslint: run via npx #2795

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Conversation

oliver-sanders
Copy link
Member

We really don't need to maintain an eslint lock file, we just need a vaguely up-to-date version.

@oliver-sanders oliver-sanders added this to the 2.3.x milestone Jun 28, 2024
@oliver-sanders oliver-sanders self-assigned this Jun 28, 2024
Comment on lines -8 to -11
"eslint-plugin-import": "^2.22.1",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-standard": "^5.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure running npx eslint would have any way of knowing about these plugin dependencies anymore

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can enable them individually (and I initially did --package a --package b ...), however, I couldn't seem to find any functional difference from removing them?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would have to add a violation to one of the rules supplied by one of these plugins to see any difference

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is what I tried yes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the latest run

ESLint couldn't find the config "standard" to extend from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants